# Page Not Found

The URL `purchase-workflow-overview/"https:/static.xcover.com/media/pds/7a51eb83-dcc6-4639-bf97-ae1cde554416/OnBuy_IPID_OkVuyYh.pdf/"` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [JS based offer display](https://docs.covergenius.com/xcover/purchase-workflow-overview/quote/js-based-offer-display.md)
- [Single Payment](https://docs.covergenius.com/xcover/purchase-workflow-overview/payment-process/single-payment.md)
- [Purchase Workflow Overview](https://docs.covergenius.com/xcover/purchase-workflow-overview.md)
- [Displaying the Quote](https://docs.covergenius.com/xcover/purchase-workflow-overview/quote/displaying-the-quote.md)
- [Dual Payment](https://docs.covergenius.com/xcover/purchase-workflow-overview/payment-process/payment.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.covergenius.com/xcover/purchase-workflow-overview/quote/js-based-offer-display.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.covergenius.com/xcover/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.covergenius.com/xcover/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/xcover/purchase-workflow-overview/quote/js-based-offer-display.md`).

You may also use `Accept: text/markdown` header for content negotiation.